Smart card driven device configuration changes

ABSTRACT

A smart card determines if the smart card has been inserted into a device, and retrieves a device identifier and at least one application configuration value from the device if the smart card has been inserted into the device. The smart card compares the retrieved device identifier and the at least one application configuration value with a device identifier and at least one application configuration value previously stored in the smart card. The smart card causes the retrieved device identifier and the at least one application configuration value to be sent to an Over The Air (OTA) server if the comparison indicates that the retrieved device identifier or the at least one application configuration value is different than the previously stored device identifier or the at least one application configuration value, so that the OTA server can supply application parameter changes to the mobile device for future device operation.

RELATED APPLICATION

The present application is a continuation of U.S. application Ser. No.12/850,678, entitled “Smart Card Driven Device Configuration Changes”and filed Aug. 5, 2010 and issued as U.S. Pat. No. 8,200,854 on Jun. 12,2012, the disclosure of which is incorporated by reference herein in itsentirety.

BACKGROUND

Smart cards typically consist of pocket-sized, or smaller, cards withembedded integrated circuits. Memory cards and microprocessor cards aretwo categories of smart cards. Memory cards contain only non-volatilememory storage components. Microprocessor cards contain memory storagecomponents and microprocessor components.

Subscriber Identity Module (SIM), Universal Integrated Circuit Cards(UICCs), and Removable User Identify (R-UIM) cards are examples ofmicroprocessor smart cards. SIM cards securely store an identifier orkey used to identify a subscriber on mobile telephone devices (e.g.,cellular radiotelephones). SIM cards enable users to change phones byremoving the SIM card from one telephony device and inserting it intoanother telephony device. UICCs are smart cards used in mobile terminalsin Global System for Mobile Communications (GSM) and Universal MobileTelecommunications System (UMTS) networks. UICCs ensure the integrityand security of different types of personal data, and may includeseveral applications that permit access to both GSM and UMTS networks.R-UIMs include cards having features that are usable with Code DivisionMultiple Access (CDMA), GSM and UMTS devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram that depicts an exemplary environment in which smartcard driven device configuration changes may be implemented;

FIG. 2 is a diagram of exemplary components of the device depicted inFIG. 1;

FIG. 3 is a diagram that depicts exemplary components of the smart carddepicted in FIG. 1;

FIGS. 4A & 4B are flow diagrams illustrating an exemplary process forimplementing smart card driven device configuration changes based on theuse of a Terminal Profile Number (TPN), a device identifier, (e.g.,IMEI), or an Application Configuration Tracking Value (ACTV) stored inboth the smart card and the device into which the smart card isinserted.

FIG. 5 is a messaging diagram associated with the exemplary process ofFIGS. 4A & 4B;

FIG. 6 is a flow diagram illustrating an exemplary process forimplementing smart card driven device configuration changes where thesmart card, instead of an OTA server, stores and supplies theapplication configuration parameter changes to the device; and

FIG. 7 is a messaging diagram associated with the exemplary process ofFIG. 6.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. The following detailed description does not limitthe invention.

Exemplary embodiments described herein employ a smart card inserted intoa device (e.g., into a mobile telephone) to drive configuration changesassociated with the operation of the mobile device. Such configurationchanges may include changes in Access Point Names (APNs), Network AccessIdentifiers (NAIs), Multi-Media Messaging Service (MMS) information,Wireless Application Protocol (WAP) information, application keys, andother data associated with the operation of the mobile device. The smartcard may include a Universal Integrated Circuit Card (UICC), a removableuser identity card (R-UIM), a subscriber identity module (SIM), auniversal subscriber identity module (USIM), or an Internet Protocol(IP) multimedia services identity module (ISIM) that may be insertedinto the device for driving the application configuration parameterchanges.

FIG. 1 is a diagram that depicts an exemplary environment 100 in whichsmart card driven device configuration changes may be implemented.Environment 100 may include a device 110, into which a smart card 120 isinserted, a smart card Over the Air (OTA) server 130, an Open MobileAlliance (OMA) Device Management (DM) OTA server 140, and a network 150.

Device 110 may include any type of electronic device that includes aninterface for inserting smart card 120. Device 110 may include any typeof communication device that uses a Universal Integrated Circuit Card(UICC)-based SIM for authentication and application enabling. Device 110may include, for example, a cellular radiotelephone, a smart phone, apersonal digital assistant (PDA), a laptop computer, a palmtop computer,a gaming device, a media player device, a tablet computer, or a digitalcamera that includes communication capabilities (e.g., wirelesscommunication mechanisms).

Smart card 120 may include any type of smart card usable for insertingin device 110 and for storing information or data relevant to theoperation of device 110. Smart card 120 may, for example, include aUniversal Integrated Circuit Card (UICC), a removable user identity card(R-UIM), a SIM, a USIM, or an ISIM.

Smart card OTA server 130 may include a server entity that maycommunicate with smart card 120 via network 150. In someimplementations, such communication may include the receipt of TerminalProfile Numbers (TPNs), device identifiers (e.g., International MobileEquipment Identities (IMEIs)) and/or Application Configuration TrackingValues (ACTVs) from smart card 120. Smart card OTA server 130 may alsocommunicate with OMA DM OTA server 140. In some embodiments (e.g., theexemplary embodiment described with respect to FIG. 6 below), smart cardOTA server 130 may send application parameters changed applicationparameters) to smart card 120 via device 110.

OMA DM OTA server 140 may include a server entity that may implement theOMA DM device management protocol for managing devices, such as forexample, mobile phones, PDAs and palm top computers. OMA DM OTA server140 may configure the devices, including device 110, by supplyingapplication parameters used in the operation of the devices, may enableand disable features of the devices, and may change settings of thedevices. OMA DM OTA server 140 may also provide software upgrades to thedevices, and may provide fault management of the devices (e.g., reporterrors from the devices, etc.). In embodiments described herein (i.e.,the exemplary embodiment described with respect to FIGS. 4A & 4B below),OMA DM OTA server 140 may send application configuration parameterchanges to device 110.

Network 150 may include one or more networks of any type, such as, forexample, a telecommunications network (e.g., a Public Switched TelephoneNetwork (PSTN) or Public Land Mobile Network (PLAIN)), a local areanetwork (TAN), a wide area network (WAN), a metropolitan area network(MAN), an intranet, the Internet, a wireless satellite network, a cablenetwork (e.g., an optical cable network), and/or one or more wirelesspublic land mobile networks (PLMNs). The PLMN(s) may include a CodeDivision Multiple Access (CDMA) 2000 PLMN, a Global System for MobileCommunications (GSM) PLMN, a Long Term Evolution (LTE) PLMN and/or othertypes of PLMNs not specifically described herein.

The configuration of environment 100 depicted in FIG. 1 is forillustrative purposes only. It should be understood that otherconfigurations may be implemented. Therefore, environment 100 mayinclude additional, fewer and/or different components than thosedepicted in FIG. 1. For example, though only a single device 110 with asingle smart card 120 is shown in FIG. 1, multiple devices 110 mayconnect to network 150, each with its own smart card 120.

FIG. 2 is a diagram of exemplary components of device 110. Device 110may include a bus 210, a processing unit 220, a main memory 230, a readonly memory (ROM) 240, a storage device 250, an input device(s) 260, anoutput device(s) 270, and a communication interface 280. Bus 210 mayinclude a path that permits communication among the elements of device200. As further shown in FIG. 2, smart card 120 may be inserted into asmart card interface (I/F) of device 110. Servers 130 and 140 may besimilar configured to device 110 shown in FIG. 2.

Processing unit 220 may include a processor, microprocessor, orprocessing logic that may interpret and execute instructions. Mainmemory 230 may include a random access memory (RAM) or another type ofdynamic storage device that may store information and instructions forexecution by processing unit 220. ROM 240 may include a ROM device oranother type of static storage device that may store static informationand instructions for use by processing unit 220. Storage device 250 mayinclude a magnetic and/or optical recording medium and its correspondingdrive.

Input device(s) 260 may include one or more mechanisms that permit anoperator to input information to device 200, such as, for example, akeypad or a keyboard, voice recognition and/or biometric mechanisms,etc. Output device(s) 270 may include one or more mechanisms that outputinformation to the operator, including a display, a speaker, etc.Communication interface 280 may include any transceiver mechanism thatenables device 200 to communicate with other devices and/or systems. Forexample, communication interface 280 may include mechanisms forcommunicating with another device or system via a network, such asnetwork 150.

Device 110 may perform certain operations or processes, as may bedescribed in detail below. Device 110 may perform these operations inresponse to processing unit 220 executing software instructionscontained in a computer-readable medium, such as memory 230. Acomputer-readable medium may be defined as a physical or logical memorydevice. A logical memory device may include memory space within a singlephysical memory device or spread across multiple physical memorydevices.

The software instructions may be read into main memory 230 from anothercomputer-readable medium, such as storage device 250, or from anotherdevice via communication interface 280. The software instructionscontained in main memory 230 may cause processing unit 220 to performoperations or processes that will be described later. Alternatively,hardwired circuitry may be used in place of or in combination withsoftware instructions to implement processes consistent with theprinciples of the invention. Thus, exemplary implementations are notlimited to any specific combination of hardware circuitry and software.

The configuration of components of device 110 illustrated in FIG. 2 isfor illustrative purposes only. It should be understood that otherconfigurations may be implemented. Therefore, device 110 may includeadditional, fewer and/or different components than those depicted inFIG. 2.

FIG. 3 is a diagram that depicts exemplary components of smart card 120.Smart card 120 may include input/output circuitry 300, a processing unit310, and a memory 320. Input/output circuitry 300 may include circuitryfor inputting data to smart card 120 from device 110, and outputcircuitry for outputting data from smart card 120 to device 110.Processing unit 310 may include a processor, microprocessor, orprocessing logic that may interpret and execute instructions. Memory 320may include RAM, ROM, and/or Electrically Erasable ProgrammableRead-Only Memory (EEPROM) that may store data (e.g., TPN, IMEI and/orACTV values), and may store instructions for execution by processingunit 310.

Smart card 120 may perform certain operations or processes, as may bedescribed in detail below. Smart card 120 may perform these operationsin response to processing unit 310 executing software instructionscontained in a computer-readable medium, such as memory 320. Acomputer-readable medium may be defined as a physical or logical memorydevice. A logical memory device may include memory space within a singlephysical memory device or spread across multiple physical memorydevices.

The software instructions contained in memory 320 may cause processingunit 310 to perform operations or processes that will be describedlater. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes consistentwith the principles of the invention. Thus, exemplary implementationsare not limited to any specific combination of hardware circuitry andsoftware.

The configuration of components of smart card 120 illustrated in FIG. 3is for illustrative purposes only. It should be understood that otherconfigurations may be implemented. Therefore, smart card 120 may includeadditional, fewer and/or different components than those depicted inFIG. 3.

FIGS. 4A and 4B are flow diagrams illustrating an exemplary process forimplementing smart card driven device configuration changes based on theuse of Terminal Profile Numbers (TPNs), device identifiers (e.g.,IMEIs), or Application Configuration Tracking Values (ACTVs) stored inboth the smart card and the device into which the smart card isinserted. The exemplary process of FIGS. 4A & 4B may be implemented bysmart card 120 in conjunction with device 110. The exemplary process ofFIGS. 4A and 4B is described with reference to the exemplary messagingdiagram of FIG. 5.

The exemplary process may include determining if smart card 120 has beeninserted into device 110 (block 400). If smart card 120 has beeninserted into device 110, smart card 120 ray retrieve TPN, IMEI, and/orACTV values (i.e., TPN_(DEV), IMEI_(DEV), ACTV_(DEV)) stored in device110 (block 405). The TPN number stored in device 110 may include one ormore parameters, originally set by the manufacture of device 110, thatmay specify device 110's hardware and/or software. Though an IMEI isdescribed herein by way of example, any type of device (or subscriber)identifier may be used for identifying device 110. Other examples ofdevice/subscriber identifiers that may be used herein include anInternational Mobile Subscriber identity (IMSI), a Mobile EquipmentIdentifier (MEID), an Electronic Serial Number (ESN), or a MobileStation International Subscriber Directory Number (MSISDN).

Smart card 120 may retrieve the TPN, IMEI, and/or ACTV values (i.e.,TPN_(CARD), IMEI_(CARD), ACTV_(CARD)) previously stored in memory 320 ofsmart card 120 (block 410). Smart card 120 may have previously receivedan IMEI number and TPN from device 110 (i.e., during block 440 below).The ACTV value may include a parameter that may initially be set to zeroif smart card 120 has never before been inserted into a device (e.g.,device 110). As described with respect to block 445 below, after smartcard 120 has been inserted into a device for a first time, smart card120 will change the ACTV value such that it is non-zero. The ACTV valuemay change each time that application configuration parameter changesare received at device 110 (e.g., changes in APN, NAI, MMS data, WAPdata, application keys, etc.)

Smart card 120 may determine if IMEI_(CARD) is not equal to IMEI_(DEV),if TPN_(CARD) is not equal to TPN_(DEV), or if ACTV_(CARD) is not equalto ACTV_(DEV)(block 415). The messaging diagram of FIG. 5 depicts smartcard 120 determining 500 if IMEI_(CARD) is not equal to IMEI_(DEV), ifTPN_(CARD) is not equal to TPN_(DEV), or if ACTV_(CARD) is not equal toACTV_(DEV). If smart card 120 determines that IMEI_(CARD) is not equalto IMEI_(DEV), TPN_(CARD) is not equal to TPN_(DEV), or ACTV_(CARD) isnot equal to ACTV_(DEV), then smart card 120 may send the values forTPN, IMEI and/or ACTV retrieved from device 110 to smart card OTA server130 (block 420). The messaging diagram of FIG. 5 depicts smart card 120sending IMEI_(DEV), TPN_(DEV) and/or ACTV_(DEV) to smart card OTA server140. Smart card OTA server 140 may then relay the values for TPN, IMEIand/or ACTV to OMA DM OTA server 150, or to another intermediate device,server, or system. The messaging diagram of FIG. 5 depicts smart cardOTA server 140 relaying IMEI_(DEV), TPN_(DEV) and/or ACTV_(DEV), to OMADM OTA server 150.

Device 110 may receive application parameter changes from OMA DM OTAserver 140 (block 425). OMA DM OTA server 140, based on the TPN, IMEIand/or ACTV values originally sent by smart card 120, may determine anychanges in application configuration parameters that may need to besupplied to device 110 for the user of device 110 to receive appropriateservices associated with the operation of device 110. The changes inapplication configuration parameters may include changes in APN, NAI,MMS data, WAP data, application keys, and/or other parameters associatedwith the operation of device 110 and with network communication servicesprovided to device 110. The messaging diagram of FIG. 5 depicts OMA DMOTA server 150 returning application configuration parameter changes 530to device 110.

Device 110 may store the changed application parameter(s) (block 430).For example, device 110 may store the changed application parameter(s)received from OMA DM OTA server 140 in main memory 230, ROM 240, orstorage device 250. Device 110 may change the TPN and/or ACTV values(i.e., TPN_(DEV), ACTV_(DEV)) stored in device 110 (block 435). The TPNand/or ACTV values may act as “change counters” with respect to changesin application configuration parameters received from OMA DM OTA server140. Therefore, processing unit 220 of device 110 may increment the TPNand/or ACTV values to new, changed values that are different than thevalues for TPN and/or ACTV prior to device 110 receiving the changedapplication configuration parameters. Device 110 may supply the changedTPN and/or ACTV values (i.e., TPN_(DEV), ACTV_(DEV)) to smart card 120(block 440). Processing unit 220 may send the changed TPN and/or ACTVvalues to smart card 120 via bus 210 and I/O circuitry 300.

Smart card 120 may replace the values of TPN and/or ACTV stored in smartcard 120 with the changed TPN and/or ACTV values received from device110 (i.e., TPN_(CARD), ACTV_(CARD) values stored in smart card 120replaced with TPN_(DEV), ACTV_(DEV) values from device 110). Forexample, processing unit 310 may set the previously stored TPN_(CARD)value equal to the TPN_(DEV) received from device 110. Additionally oralternatively, processing unit 310 may set the previously storedACTV_(CARD) value equal to the ACTV_(DEV) value received from device110.

FIG. 6 is a flow diagram illustrating an exemplary process forimplementing smart card driven device configuration changes where smartcard 120, instead of an OTA server, stores and supplies the applicationconfiguration parameter changes to device 110. The exemplary process ofFIG. 6 may be implemented by smart card 120 in conjunction with device110. The exemplary process of FIG. 6 is described with reference to theexemplary messaging diagram of FIG. 7.

The exemplary process may include determining if smart card 120 has beeninserted into device 110 (block 600). The messaging diagram of FIG. 7depicts smart card 120 being inserted 700 into device 110. If smart cardhas been inserted into device 110, smart card 120 may push theapplication configuration parameter(s) stored in memory 320 to device110 (block 610). Smart card 120 may have previously received applicationconfiguration parameters (APN, NAI, MMS data, WAP data, applicationkeys, etc.) from smart card OTA server 140 and may have stored thoseparameters in memory 320. Therefore, smart card 120, upon insertion intodevice 110, automatically supplies device 110 with applicationconfiguration parameters that may be used in the operation of device110. The messaging diagram of FIG. 7 depicts smart card 120 supplyingthe application configuration parameters 710 to device 110.

Smart card 120 may determine if application parameter changes have beenreceived at smart card 120 (block 620). Smart card OTA server 140 mayautomatically send updated application configuration parameters to smartcard 120. For example, as shown in the messaging diagram of FIG. 7,smartcard OTA server 140 may send application configuration parameterchanges 720 to smart card 120. If application configuration parameterchanges have not been received at smart card 120, then smart card 120may determine if it has been removed from device 110 (block 630). Ifsmart card 120 has not been removed from device 110 (NO—block 630), thenthe exemplary process may return to block 620. If smart card 120 hasbeen removed from device 110 (YES—block 630), then device 110 may resetthe application configuration parameters stored in device 110 (block640). Resetting the application configuration parameters may includechanging them back to their default values.

Returning to block 620, if application configuration parameter changesare received at smart card 120, then smart card 120 may store thechanged application configuration parameters in memory 320 (block 650).Smart card 120 may then push the changed application configurationparameter(s) to device 110 (block 660). The messaging diagram of FIG. 7depicts the changed application configuration parameters 730 beingsupplied via smartcard 120 to device 110. Upon receipt of the changedapplication configuration parameters, device 110 may store theparameters in main memory 230, ROM 420 or storage device 250 for futureuse.

As described herein, exemplary embodiments utilize a smart card insertedinto a device (e.g., a mobile telephone) to drive configuration changesassociated with the operation of the device. Such configuration changesmay include changes in APNs, NAIs, MMS information, WAP information,application keys, and other data associated with the operation of themobile device.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention. For example, while series of blocks have beendescribed with regard to FIGS. 4A, 4B and 6, the order of the blocks maybe modified in other embodiments. Further, non-dependent blocks may beperformed in parallel.

Certain features described above may be implemented as “logic” or a“unit” that performs one or more functions. This logic or unit mayinclude hardware, such as one or more processors, microprocessors,application specific integrated circuits, or field programmable gatearrays, software, or a combination of hardware and software.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

What is claimed is:
 1. A method, comprising: determining if a smart cardhas been inserted into a device; retrieving, if the smart card has beeninserted into the device, application configuration parameterspreviously stored in the smart card; pushing, responsive to the smartcard being inserted into the device, the retrieved applicationconfiguration parameters, from the smart card to the device, for use indevice operations; receiving subsequent application configurationparameter changes at the smart card from an Over the Air (OTA) server;storing the application configuration parameter changes at the smartcard; pushing the received application parameter changes from the smartcard to the device for use in device operations; determining if thesmart card has been removed from the device; and resetting theapplication configuration parameter changes stored in the device todefault values responsive to the smart card being removed from thedevice.
 2. The method of claim 1, wherein the smart card comprises aUniversal Integrated Circuit Card (UICC), a removable user identity card(R-UIM), a subscriber identity module (SIM), a universal subscriberidentity module (USIM), or an Internet Protocol (IP) multimedia servicesidentity module (ISIM).
 3. The method of claim 1, wherein the devicecomprises a device having wireless communication mechanisms.
 4. Themethod of claim 1, wherein the device comprises one of a cellularradiotelephone, a smart phone, a personal digital assistant (PDA), alaptop computer, a palmtop computer, a gaming device, a media playerdevice, a tablet computer, or a digital camera.
 5. The method of claim1, wherein the device comprises a communication device that uses aUniversal Integrated Circuit Card (UICC)-based subscriber identitymodule (SIM) for authentication and application enabling.
 6. The methodof claim 1, wherein the application configuration parameters compriseone or more of an Access Point Name (APN), a Network Access Identifier(NAI), Multi-Media Messaging Service (MMS) information, WirelessApplication Protocol (WAP) information, or one or more application keys.7. A smart card, comprising: input/output circuitry configured tointerface with a device; a memory; a processing unit configured to:retrieve from the device, when the smart card is inserted into thedevice, a first application configuration change counter that trackschanges in one or more application configuration parameters associatedwith operation of the device, compare the retrieved first applicationconfiguration change counter with a second application configurationchange counter previously stored in the memory of the smart card, causethe retrieved first application configuration change counter to be sentto an Over The Air (OTA) server based on the comparison, receive amodified version of the first application configuration change counterfrom the device via the input circuitry, wherein the device generatedthe modified version of the first application configuration changecounter value based on receiving changes in the one or more applicationconfiguration parameters from the OTA server, and replace, in thememory, the previously stored second application configuration changecounter with the modified version of the first application configurationchange counter.
 8. The smart card of claim 7, wherein the one or moreapplication configuration parameters comprise one or more of an AccessPoint Name (APN), a Network Access Identifier (NAI), Multi-MediaMessaging Service (MMS) information, Wireless Application Protocol (WAP)information, or application keys.
 9. The smart card of claim 7, wherein,when comparing the retrieved first application configuration changecounter with the second application configuration change counterpreviously stored in the memory, the processing unit is furtherconfigured to: determine if the first application configuration changecounter is different than the previously stored second applicationconfiguration change counter.
 10. The smart card of claim 7, wherein thesmart card comprises a Universal Integrated Circuit Card (UICC), aremovable user identity card (R-UIM), a subscriber identity module(SIM), a universal subscriber identity module (USIM), or an InternetProtocol (IP) multimedia services identity module (ISIM).
 11. The smartcard of claim 7, wherein the first application configuration changecounter comprises a Terminal Profile Number (TPN) or an ApplicationConfiguration Tracking Value (ACTV).
 12. A method, comprising:retrieving, at a smart card, a first application configuration changecounter that tracks changes in one or more application configurationparameters associated with operation of a device with which the smartcard is used; comparing, at the smart card, the retrieved firstapplication configuration change counter with a second applicationconfiguration change counter previously stored in the smart card toproduce a first comparison; sending the retrieved first applicationconfiguration change counter to an Over The Air (OTA) server based onthe first comparison; receiving, at the device from the OTA server,changes in the one or more application configuration parameters;modifying, at the device, the first application configuration changecounter; and replacing, in the smart card, the previously stored secondapplication configuration change counter with the modified firstapplication configuration change counter.
 13. The method of claim 12,wherein the one or more application configuration parameters compriseone or more of an Access Point Name (APN), a Network Access Identifier(NAI), Multi-Media Messaging Service (MMS) information, WirelessApplication Protocol (WAP) information, or application keys.
 14. Themethod of claim 12, wherein retrieving the first applicationconfiguration change counter comprises: retrieving, at the smart card,the first application configuration change counter when the smart cardis inserted into the device.
 15. The method of claim 12, wherein sendingthe retrieved first application configuration change counter to an OverThe Air (OTA) server further comprises: sending the first applicationconfiguration change counter to the OTA server if the first comparisonindicates that the first application configuration change counter isdifferent than the previously stored second application configurationchange counter.
 16. The method of claim 12, further comprising:retrieving, at the smart card from the device, a first device identifierassociated with the device, in conjunction with retrieving the firstapplication configuration change counter.
 17. The method of claim 16,further comprising: comparing, at the smart card, the retrieved firstdevice identifier with a second device identifier previously stored inthe smart card to produce a second comparison, and wherein sending theretrieved first application configuration change counter to the OTAsserver is further based on the second comparison.
 18. The method ofclaim 12, wherein the smart card comprises a Universal IntegratedCircuit Card (UICC), a removable user identity card (R-UIM), asubscriber identity module (SIM), a universal subscriber identity module(USIM), or an Internet Protocol (IP) multimedia services identity module(ISIM).
 19. The method of claim 12, wherein the device comprises adevice having wireless communication mechanisms and wherein the devicecomprises one of a cellular radiotelephone, a smart phone, a personaldigital assistant (PDA), a laptop computer, a palmtop computer, a gamingdevice, a media player device, a tablet computer, or a digital camera.20. The method of claim 12, wherein modifying the first applicationconfiguration change counter further comprises incrementing the firstapplication configuration change counter, and wherein replacing thepreviously stored second application configuration change counterfurther comprises replacing the previously stored second applicationconfiguration change counter with the incremented first applicationconfiguration change counter.